Skip to content

chore: release v24.0.0 - #8055

Merged
PastaPastaPasta merged 2 commits into
dashpay:v24.0.xfrom
PastaPastaPasta:release/v24.0.0
Nov 5, 2026
Merged

PastaPastaPasta merged 2 commits into
dashpay:v24.0.xfrom
PastaPastaPasta:release/v24.0.0

Conversation

@PastaPastaPasta

@PastaPastaPasta PastaPastaPasta commented Nov 4, 2026 •

Copy link
Copy Markdown
Member

Issue being fixed or feature implemented

v24.0.x is at v24.0.0-rc.7 (111a2c533e) and still builds as a pre-release: CLIENT_VERSION_IS_RELEASE is false, so the binaries show the "This is a pre-release test build" warning. The final tag needs that flag set, and the v24.0.0 release notes don't yet list v23.1.10 (released Nov 2), which shipped after the notes were written.

What was done?

  • configure.ac: set _CLIENT_VERSION_IS_RELEASE to true. The version is already 24.0.0.

  • doc/release-notes/dash/release-notes-23.1.10.md: archive the v23.1.10 notes, copied byte for byte from the v23.1.10 tag.

  • doc/release-notes.md: add v23.1.10 to "Older releases" and start the "set of changes" link from v23.1.10 instead of v23.1.9. v23.1.10 is the last release before v24.0.0 and is an ancestor of this branch.

  • contrib/flatpak/org.dash.dash-core.metainfo.xml: add the 23.1.10 entry, copied from the v23.1.10 tag (2026-10-30, the date that tag recorded). The 24.0.0 entry dated 2026-11-05 was already there.

Nothing else changes. Code, consensus and activation parameters, chainparams, seeds, translations and man pages are as they were at rc.7. Those were updated earlier in #7974, #7982 and #7989.

How Has This Been Tested?

  • git diff v24.0.0-rc.7 touches only the four files above. In configure.ac the only change is the _CLIENT_VERSION_IS_RELEASE line.
  • The archived notes match git show v23.1.10:doc/release-notes.md exactly (cmp).
  • CI runs on the PR head and is linked from this PR.
  • xmllint --noout passes on the metainfo file.
  • Local build of 202632c83c on macOS with Homebrew Autoconf 2.73 (the later metainfo commit doesn't affect the build). This passed only with a local workaround, so it isn't a clean build pass:
    • ./autogen.sh && ./configure succeeds, and the generated src/config/bitcoin-config.h has #define CLIENT_VERSION_IS_RELEASE true.
    • The first make -C src dash-cli failed with bitcoin-cli.cpp:151:32: error: use of undeclared identifier 'PACKAGE_NAME'. This Autoconf leaves all six PACKAGE_* macros as #undef in the generated header, although configure sets them in confdefs.h.
    • Apart from the release flag, the build inputs are the same as rc.7, so this is a local toolchain issue. Guix builds use their own autotools.
    • After copying the six PACKAGE_* defines from configure's confdefs.h into the generated, untracked header, dash-cli and warnings.cpp compiled. No tracked file was changed.
    • dash-cli -version prints Dash Core RPC client version v24.0.0. The compiled warnings.o no longer contains the "pre-release test build" string.

Breaking Changes

None.

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have made corresponding changes to the documentation
  • I have assigned this pull request to a milestone

🤖 Generated with Claude Code

Set CLIENT_VERSION_IS_RELEASE to true, archive the v23.1.10 release notes
and start the v24.0.0 change log from v23.1.10, the last release before it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@PastaPastaPasta PastaPastaPasta added this to the 24 milestone Nov 4, 2026
@thepastaclaw

thepastaclaw commented Nov 4, 2026 •

Copy link
Copy Markdown
Collaborator

🕓 Review not started yet because the new head is waiting for the 30-minute push debounce.

  • Request normal review — click when the PR is ready for review.
  • Request priority review — click to move this review to the front of the queue.

Commit d6c066f. Normal review starts when eligible; priority review starts as soon as a slot is available.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@PastaPastaPasta
PastaPastaPasta marked this pull request as ready for review November 5, 2026 03:09
@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ⚠️ Failed 2026-11-05T03:09:41.428393Z
We couldn’t complete this review. Comment @codex review to try again.
d6c066f Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@PastaPastaPasta
PastaPastaPasta merged commit 938fba5 into dashpay:v24.0.x Nov 5, 2026
47 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants